Code coverage increase, and manual code trigger - src/flags.js #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
September 3, 2024 14:03
Pull Request Test Coverage Report for Build 10719743949Details
💛 - Coveralls |
mrahmed2026
changed the title
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was able to increase the overall code coverage of this file.
83.26% Statements 408/490 67.34% Branches 165/245 82.69% Functions 86/104 83.87% Lines 390/465
85.3% Statements 418/490 71.02% Branches 174/245 84.61% Functions 88/104 86.02% Lines 400/465
This was indicated in the npm run test locally, and on the code coverage tool, and shown to Professor Eduardo as well.
Further, I addded a console log to the flag.js file and it was shown after i triggered the code, by flagging a blog post or annoucement.